Board Logs

These logs are identified by a board ID ("BID"). Example of a board Syslog message:

10:21:28.037 : 10.15.7.95 : NOTICE : [S=872] [BID=3aad56:32] Activity Log: WEB: Successful login at 10.15.7.95:80. User: Admin. Session: HTTP (10.13.22.54)

Unique non-SIP session related (e.g., device reset or a Trunk alarm) and device identifier

The device identifier facilitates debugging by clearly identifying the specific device that sent the log message, especially useful in deployments consisting of multiple devices.

In addition, the benefit of unique numbering is that it enables you to filter the information according to device.

Syntax of the BID: [BID=<last 6 characters in MAC>:<number of times device has reset>]

Example:

14:32:52.062: 10.33.8.70: WARNING: [S=9399] [BID=2ed1c8:96] invalid Physical index

Where:

■

2ed1c8 is the device's MAC address.

■

96 is the number of times the device has reset.

For later software versions of Mediant Software and Mediant 9000, instead of MAC address, the BID contains the serial number.

Example: Event in syslog indicating a TLS socket debug message:

11:36:55.220  10.15.45.49  local0.notice  [S=12614860] [BID=50e91b:74]  (N 11900116)  TLSSocketAPI(#67) Socket debug message: CTcpClientSocket::HandleSocketEvent socket close/resetSocketName: SIPTcpChild, FileDesc: 75  [Time:17-02@09:36: